The interface is the argument

I spent the first four years of my career believing that design was decoration applied to a decision someone else had already made. Someone wrote the spec, someone built the thing, and I made it pleasant. That belief cost me a lot of good work.

Here is the correction, and it took an embarrassingly long time: every interface is an argument. It is making a case. Put a button somewhere and you have claimed that this action matters more than the seven others you buried in a menu. Set a default and you have told the majority of your users what you think they want, and most of them will never disagree with you, because most people never change a default. That is not decoration. That is the product having an opinion.

The argument you didn't mean to make

The trouble is that an interface makes its argument whether or not you meant one. If nobody decides what the screen is for, it argues for whatever was easiest to build. I have shipped screens like that. They tend to have four equally weighted buttons across the top, because four teams each wanted their thing to be visible and nobody wanted to be the one who said no.

A screen with four equal priorities has no priorities. The user reads it as noise and picks the leftmost thing, or leaves.

If you cannot say in one sentence what the screen wants the person to do, the screen does not know either.

So I write the sentence first now. Before any layout. This screen exists so that a studio owner can see what is booked next week and move one job without calling anybody. That sentence kills features. It has to — that is what it is for. Every element that does not serve it is now visibly on trial, and most of them lose.

Hierarchy is just the argument, rendered

Once you have the sentence, the visual work becomes almost mechanical. The thing the sentence names gets the most weight: bigger, heavier, higher, more contrast, more space around it. The supporting cast gets less. The rest goes behind a click.

People call this taste. It mostly isn't. It is having decided, and then being consistent about the decision. Taste is what you need for the last ten percent — which of two equally correct hierarchies feels better, whether this spacing is generous or merely large. The first ninety percent is just refusing to leave the argument unmade.

What this changed for me

Three things, concretely.

• I stopped starting in a design tool. I start in a text file, with the sentence.
• I stopped asking stakeholders what they want on the screen and started asking what the person is trying to finish.
• I got much better at saying no, because the no is no longer my preference against theirs. It is the sentence against their request, and the sentence was agreed on in the room.

That last one is the whole trick, honestly. Design arguments get personal when they are taste versus taste. They stop being personal the moment there is a written sentence on the wall that everyone signed off on, and the only question is whether this button serves it.

It does not make you right. It makes you legible, which is better.